Eliminate xtime and its member sec, nsec#3594
Eliminate xtime and its member sec, nsec#3594StephanTLavavej merged 6 commits intomicrosoft:mainfrom
xtime and its member sec, nsec#3594Conversation
|
Thanks! As I mentioned on Discord, I would indeed like to see all of the non-Standard functions be removed, limited only by anything that affects ABI. (Stuff that's separately compiled is generally clear because either the class is marked as exported, or the functions are marked, and there are explicit calling conventions so they look "weird". You can also double-check the export surface with |
And make one `_Wait_until_sys_time` private.
|
Thanks, I agree that this should preserve ABI. Leaving the parameter names as |
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
|
Thanks for carefully removing this non-Standard machinery that was allowing calls like |
This PR is currently trying to replace uses of
xtimewith_timespec64, because_timespec64istimespec, and<time.h>, andxtime.Definition of
_timespec64(not available in this repo):Definition of
xtime:STL/stl/inc/xtimec.h
Lines 23 to 26 in 5e60382
Working towards #2206.
Every function in MSVC STL that has external linkage and involves
xtimeis eitherextern "C"or inline, so I think this PR doesn't break ABI.I'm also trying to change the name of every function, except for constructor, involvingxtime/_timespec64in order to avoid polluting overload sets.For constructor ofunique_lock, I'm adding an explicit construction tag type - perhaps we can simply remove that ctor, and some other non-standard functions.Edit: This PR is now removing non-standard overloads. One non-standard
condition_variable::wait_untiloverload is changed to_Wait_until_sys_timeand madeprivate.